Problem Note 52087: SAS® Data Integration Studio jobs fail with errors due to metadata server connectivity issues
 |  |  |  |  |
SAS statements like LIBNAME and PROC METALIB or DATA Step statements that require connecting back to the metadata server might fail with the following errors at execution time:
-
ERROR: Libname LIBREF is not assigned. ERROR: Error in the LIBNAME statement. ERROR 52-121: Invalid credentials ERROR: Access denied.
-
ERROR: DBMS connection error: invalid username/password; logon denied. ERROR: Error in the LIBNAME statement.
-
NOTE: Connecting to SAS Metadata Server produced: ERROR: Invalid credentials NOTE: SAS application server not found; the local machine will be used.
-
NOTE: Connecting to SAS Metadata Server produced: ERROR: Cannot locate the metadata for SAS Application Server "AppServer"
These errors occur when the following conditions are true:
- The SAS Data Integration Studio job contains code that sets the SAS system option METASERVER.
- The value specified on the METASERVER system option does not match the metadata server information that was established during trusted peer initialization.
The METASERVER system option is not required and should not be present in job code, but it is generated in the code when the SAS Data Integration Studio job option, Enable optional metadata macro variables, is set to Yes. In prior releases of SAS Data Integration Studio, it was necessary to set the METASERVER system option (along with METAPORT). However, trusted peer connectivity has removed that need.
The workaround for this issue is to select No for the Enable optional metadata macro variables job option in order to prevent the METASERVER system option from being set. Perform the following steps to modify the job option setting:
- Open properties on the job.
- Click the Options tab.
- Select No for the option Enable optional metadata macro variables.
- Click OK to save the change.
The setting of the METASERVER and METAPORT system options will be removed from code generation in a future release of the product.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Data Integration Studio | Microsoft Windows Server 2003 Standard Edition | 4.3 | 9.3 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 4.3 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2003 for x64 | 4.3 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2008 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Microsoft Windows Server 2008 R2 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Microsoft Windows Server 2008 for x64 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Microsoft Windows XP Professional | 4.3 | 9.3 TS1M0 | ||||
| Windows 7 Enterprise 32 bit | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows 7 Enterprise x64 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows 7 Home Premium 32 bit | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows 7 Home Premium x64 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows 7 Professional 32 bit | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows 7 Professional x64 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows 7 Ultimate 32 bit | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows 7 Ultimate x64 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||
| Windows Vista | 4.3 | 9.3 TS1M0 | ||||
| Windows Vista for x64 | 4.3 | 9.3 TS1M0 | ||||
| Microsoft Windows Server 2003 Datacenter Edition | 4.3 | 9.3 TS1M0 | ||||
| Microsoft® Windows® for x64 | 4.3 | 4.902 | 9.3 TS1M0 | 9.4 TS1M4 | ||